16/03/2025 - 22/03/2025

20/03/2025 14:30

Performance of pattern finding (reminder):
a4ef7a8672b36935a7068ff0d3820ddc.png

Sean and I met to discuss the problems with the pattern finder. Our current idea is that there are two main failing points:

Tracklets line fitting being skewed causing improper distance calculation

Example:
Truth:
edfae3b86aa0db07fc0df97d826d2990.png

Reconstruction:
39bfce4d6c36c3411df690f73596ff57.png

Potential Solution:
In general, we need a better fitter. How to go about that (and at what stage) is unclear. One option is to only do linear fits near the stop and start of tracks (preventing "pull" from scattering). Another option is to have a more robust fitter that considers scattering like seen above.

Particles (like Bhabas) being created far from tracklet endpoints

Example
Truth:
89c348205df6c84dd8427de7a4be3791.png

Reconstruction
bcfdc4a91694cb137742cab1dca4f67b.png

Potential Solution:
First, it's unclear whether or not these electrons will be accurately resolved by the tracklet finder (or if they even need to be).

Assuming these electron tracklets are accurately resolved, we instead need to project tracklet starts onto some finite space (ex. line segment). That way, the distance calculation will be based on how close the new tracklets start is to an existing tracklet as a whole, not just the endpoints of another tracklet. If this is more computationally expensive, it can be done as a "second pass", i.e. the original method of just comparing endpoint distances can be done first.


20/03/2025 14:41

Some discussion points for Jessie:

  1. How much info from tracklet finding (all hits vs some fit)
    1. If we have a fit, how much information are we getting from that?
  2. (maybe for Patrick) how much computatation resources can we spare? I.e. how fast does this need to be.